🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

We're still going to be missing math support: https://theaccessibilityguy.com/how-to-use-latex-for-accessible-math-in-pdfs/

The docs suggest to use lualatex-dev to compile the document. Can we support that by setting pdf-engine?

Yes it should, but is lualatex-dev ship with TeX Live ?

On my installation I don't see it

❯ ls C:\Users\chris\AppData\Roaming\TinyTeX\bin\windows\lua*

    Directory: C:\Users\chris\AppData\Roaming\TinyTeX\bin\windows

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a---          23/07/2025    17:19         215040 lua53w64.dll
-a---          23/07/2025    17:19        7132160 luahbtex.dll
-a---          23/07/2025    17:19           6656 luahbtex.exe
-a---          23/07/2025    17:19           6656 lualatex.exe
-a---          23/07/2025    17:19           6144 luaotfload-tool.exe
-a---          23/07/2025    17:19        6097408 luatex.dll
-a---          23/07/2025    17:19           6656 luatex.exe

I found an old Dockerfile from last year that I had written to experiment with tagging. This is what I used:

FROM pandoc/latex
RUN tlmgr install \
        l3experimental \
        latex-base-dev \
        latex-bin-dev \
        pdfmanagement-testphase \
        tagpdf && \
    mv /opt/texlive/texdir/bin/default/lualatex \
        /opt/texlive/texdir/bin/default/lualatex-original && \
    ln -s /opt/texlive/texdir/bin/default/lualatex-dev \
          /opt/texlive/texdir/bin/default/lualatex

I think the linking was necessary because pandoc doesn't accept a program named lualatex-dev as the LaTeX compiler.

For what's worth, I didn't need to call lualatex-dev in order for the document to be tagged. Locally for me at least, it worked with just lualatex.

Add support for code cells:

---
format:
  pdf:
    tagpdf: true
    keep-tex: true
title: This is a tagpdf test
---

## This is a test

![A caption](./an-image.png){fig-alt="alt text 2 here"}

```{r}
#| label: fig-test
#| fig-cap: This is a caption
#| fig-alt: This is the alt text
plot(1:100)
```

See @fig-test.

Sophie and Sam told me the tagpdf package actually warns users of missing alt text. We should pull those warnings and show them.

Also, alt text for cover image (it's in metadata + partials so will need extra care)

This is fairly disappointing, but we've hit a blocker issue in Pandoc 3.7.0.2 and need to push this to 1.9 (specifically, we need to push this to after we start using quarto-dev/quarto-markdown)

Specifically, we're blocked by #13249

I've been playing with the changes here along with Pandoc 3.8.3.
I needed to alter the test file, tagpdf.qmd, to target latex (to avoid an error when the image isn't found):

---
format:
  latex:
    tagpdf: true
    keep-tex: true
title: This is a tagpdf test
_quarto:
  tests:
    latex:
      ensureFileRegexMatches:
        - 
          - "tagging = on"
          - 'alt={alt text 2 here}'
        - []
---

## This is a test

![A caption](./an-image.png){fig-alt="alt text 2 here"}

This test passes with Pandoc 3.8.3, but we should add the following, currently failing, examples:

---
format:
  latex:
    tagpdf: true
    keep-tex: true
title: This is a tagpdf test
_quarto:
  tests:
    latex:
      ensureFileRegexMatches:
        - 
          - "tagging = on"
          - 'alt={alt text 1 here}'
          - 'alt={alt text 2 here}'
          - 'alt={alt text 3 here}'
        - []
---

## This is a test

![A caption](./an-image.png){fig-alt="alt text 2 here"}

![](./an-image.png){fig-alt="alt text 1 here"}

![A caption](./an-image.png){#fig-3 fig-alt="alt text 3 here"}

Thank you for your continued work on this important feature!

Just wanted to let you know that I recently learned that the tagpdf LaTeX package is currently incompatible with KOMA classes (Quarto's default Document Class option). In the "Tagging Status of LaTeX Packages and Classes" table, I believe it's associated with the scrartcl entry. This led to an issue described here, wherein the tagged PDF had an empty table tag (there were no tables in the document) that made the Adobe Accessibility Check fail a table-related test.

Luckily, there seems to be a straightforward fix: in the yaml, specify the documentclass as something other than a KOMA script class. I succeeded when using the report class, like this:

---
title: "My title"
format:
  pdf:
    documentclass: report
keep-tex: true
---

Closing in favor of #13857